keywords: ip pbx voip gateway gsm gateway

×

Notice

The forum is in read only mode.
× Questions about B100/200/400/800 ISDN BRI Cards

B200P/B400P hfcmulti_rx: CRC-error

13 years 6 months ago #6278 by lisa.gao
Hi,
1. For your problem one: Do you have any problem with the error?
2. For your problem two: Please change another PCI slot to have a try.


Best regards!

13 years 6 months ago #6279 by james.zhu
hello:
regarding the questions:
1) please give our ssh, we have to check the versions and recompile that(if necessary).
2) please check this: "with riser extension for PCI", it might be a problem caused with..

13 years 6 months ago #6280 by nedim.zecic
@lisa.gao
1. No. It works like a charm.
2. I did that. I will test it this week.

@james.zhu
1. Sorry, but at this moment my client is not willing to give access because this is production call center.
2. I assumed that. Now I've changed PCI slot and will see what happens. Is it possibile that PCI does not have enough power to feed the card?

Today I've replaced all cables and checked all connections between NTs and B400P. Additionaly I've replaced the one NT that was different and now all NTs are Sphairon NT1Q. And this is my dmesg with spharion NTs after reboot:

1 devices registered
mISDN_dsp: Audio DSP Rev. 1.29 (debug=0x0) EchoCancellor MG2 dtmfthreshold(100)
mISDN_dsp: DSP clocks every 64 samples. This equals 8 jiffies.
eth0: no IPv6 routers present
hfcmulti_rx: CRC-error
hfcmulti_rx: CRC-error
hfcmulti_rx: CRC-error
Bluetooth: Core ver 2.10
...
As you can see now I have 3 crc errors. So in my opinion these errors are related to NTs in my case. Do you think I should plug external power to NTs?

Thanks
13 years 6 months ago #6281 by lisa.gao
Hi,
Yes, NT mode need to be provided external power . You need to plug the external power supply.


Best regards!

13 years 6 months ago #6290 by nedim.zecic
Nope,

Connecting external power to NTs did not solve hfcmulti_rx: CRC-error. However it seems now that errors are reduced. Somehow this issue is related to NTs.
Next I will check cables for possible interference with incoming lines.
13 years 6 months ago #6291 by nedim.zecic
One more strange thing I've noticed. After loading mISDN, the driver keeps L1 and L2 links up. This is strange because my telco is shutting them down after a few seconds. When first calls are processed through these 3 ports links are going down which is correct behavior. This is my "misdn show stacks" after the driver is loaded:
* Port 1 Type TE Prot. PMP L2Link UP L1Link:UP Blocked:0 Debug:0
* Port 2 Type TE Prot. PMP L2Link UP L1Link:UP Blocked:0 Debug:0
* Port 3 Type TE Prot. PMP L2Link UP L1Link:UP Blocked:0 Debug:0
* Port 4 Type TE Prot. PMP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0
I've waited almost 15 minutes and links aren't going down. But after few calls are accomplished everything works like it should:
* Port 1 Type TE Prot. PMP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0
* Port 2 Type TE Prot. PMP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0
* Port 3 Type TE Prot. PMP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0
* Port 4 Type TE Prot. PMP L2Link DOWN L1Link:DOWN Blocked:0 Debug:0
Time to create page: 0.043 seconds
Powered by Kunena Forum